From: Adrian Robert Date: Fri, 6 Mar 2009 19:07:00 +0000 (+0000) Subject: Include for SIGTERM used in ns_term_shutdown. X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1~1^2~421^2~1380 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=2709b3b7dd2c1c6ab1f10f07bd91ae82e9181ceb;p=emacs.git Include for SIGTERM used in ns_term_shutdown. --- diff --git a/src/nsterm.m b/src/nsterm.m index 6ebf49f77c1..1b7301084d0 100644 --- a/src/nsterm.m +++ b/src/nsterm.m @@ -32,6 +32,7 @@ GNUstep port and post-20 update by Adrian Robert (arobert@cogsci.ucsd.edu) #include #include #include +#include #include #include "lisp.h" @@ -4474,13 +4475,12 @@ extern void update_window_cursor (struct window *w, int on); if (![[self window] isKeyWindow]) { - /* XXX: Using NO_SOCK_SIGIO like Carbon causes a condition in which, - when Emacs display updates a different frame from the current one, - and temporarily selects it, then processes some interrupt-driven - input (dispnew.c:3878), OS will send the event to the correct NSWindow, - but for some reason that window has its first responder set to the - NSView most recently updated (I guess), which is not the correct one. - UPDATE: After multi-TTY merge this happens even w/o NO_SOCK_SIGIO */ + /* XXX: There is an occasional condition in which, when Emacs display + updates a different frame from the current one, and temporarily + selects it, then processes some interrupt-driven input + (dispnew.c:3878), OS will send the event to the correct NSWindow, but + for some reason that window has its first responder set to the NSView + most recently updated (I guess), which is not the correct one. */ if ([[theEvent window] isKindOfClass: [EmacsWindow class]]) [(EmacsView *)[[theEvent window] delegate] keyDown: theEvent]; return;